Bump Plutus deps to 1.11 #3680
Merged
Bump Plutus deps to 1.11 #3680
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lehins
requested changes
Aug 25, 2023
There was a problem hiding this comment.
Whenever bounds in a cabal file are changed the patch version of the package needs to be increased, otherwise the package will not get released next time we'll be going through a release process. So, could you please bump the last number in versions for these packages:
- cardano-ledger-alonzo-test
- cardano-ledger-binary
bezirg
force-pushed
the
bezirg/plutus-1.11.0.0
branch
2 times, most recently
from
9951c05 to
e807f6f
Compare
lehins
force-pushed
the
bezirg/plutus-1.11.0.0
branch
from
e807f6f to
826fe84
Compare
lehins
force-pushed
the
bezirg/plutus-1.11.0.0
branch
from
826fe84 to
9141820
Compare
lehins
approved these changes
Sep 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Checklist
.cabalandCHANGELOG.mdfiles according to theversioning process.
.cabalfiles for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)CHANGELOG.mdfor the affected packages. New section is never added with the code changes. (See RELEASING.md)fourmolu(usescripts/fourmolize.sh)scripts/cabal-format.sh)hie.yamlhas been updated (usescripts/gen-hie.sh)